Fix FTBFS with recent GCC#3633
Merged
Merged
Conversation
Signed-off-by: Peter Lemenkov <lemenkov@gmail.com>
bogdan-iancu
added a commit
that referenced
this pull request
Apr 24, 2025
Fix FTBFS with recent GCC (cherry picked from commit 4f1059b)
bogdan-iancu
added a commit
that referenced
this pull request
Apr 24, 2025
Fix FTBFS with recent GCC (cherry picked from commit 4f1059b)
NormB
pushed a commit
to NormB/opensips
that referenced
this pull request
May 9, 2026
Fix FTBFS with recent GCC
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes building with a very modern GCC which does even better type checking.
Details
GCC 15 treats declarations like
int foo();differently. In C23 (a default for GCC 15), it's equivalent toint foo(void);whereas, in earlier versions of C, such a declaration plays fast and loose with the type system — essentially meaning, "we don't know how many parameters this function takes or their types; let's hope your code is correct!".I've updated code accordingly and fixed other type incompatibility.
Compatibility
Builds file with both modern GCC 15 and older version.